@SpiderKenny You can use sshpass, here's my rough notes on how to use it to deploy firmware using scp and ssh with sshpass: // using sshpass to deploy new firmware ssh-keygen -f "/home/chris/.ssh/known_hosts" -R "fe80::42a3:6bff:fec3:cb5b%enp0s31f6" sshpass -ponioneer scp -6 -o StrictHostKeyChecking=no ~/source/bin/targets/ramips/mt76x8/openwrt-ramips-mt76x8-omega2p-squashfs-sysupgrade.bin root@[fe80::42a3:6bff:fec3:cb5b%enp0s31f6]:/tmp sshpass -ponioneer ssh -6 -o StrictHostKeyChecking=no root@fe80::42a3:6bff:fec3:cb5b%enp0s31f6 sysupgrade -n /tmp/openwrt-ramips-mt76x8-omega2p-squashfs-sysupgrade.bin fe80::42a3:6bff:fec3:cb5b

Did you try ssh root@hostname.local ? See the difference it makes to ping on my setup:

@Waqas Onion is based upon OpenWrt which uses Dropbear as the sshd so you configure it in /etc/config/dropbear, or uci commands, by default it listens on all interfaces but you can add the interface option to specify a specific interface.You can also have multiple different configurations, I'm not sure what the limit is but I use 2 myself, one for local LAN and another for WAN port forwarded. Take a look at https://openwrt.org/docs/guide-user/base-system/dropbear

@Kate Pls try the sshfs extension, to see if that works for you. MS always makes it "awesome".. A: Onion side # onion os version (just FYI) === Version Info === Omega firmware: v0.3.2 b242 onion-os - 1.0.6-1 1: Set a passwd for the omega user to connect from your workstation over ssh, passwd is the easiest way. # passwd B: Workstation side 1: Install SSH FS extension for VSCode in the VS https://marketplace.visualstudio.com/items?itemName=Kelvin.vscode-sshfs $ ext install Kelvin.vscode-sshfs or DL the vsix & add to VSCode https://open-vsx.org/api/Kelvin/vscode-sshfs/1.25.0/file/Kelvin.vscode-sshfs-1.25.0.vsix 2: SSH-FS shall create its own icon in the left panel, under "Soucre-Control","Extensions" etc. Click on it to setup the new ssh connection/credentials (IP, username, remote folder etc), pointing to omega. 3: Click on the "Folder+:" icon under the new connection entry. This will effectively add the remote folder to the current workspace. You will be prompted for the passwd, if that was left blank in #2. The connection also gives a shell prompt. Any file that is created under the newly added "remote" folder shall be created physically under the remote folder. "Save" to apply code changes. The plugins (C/++, Python etc) that you have installed in your WS works as usual, while you code. My workstation is Linux, so there was no need to install any ssh client. If you are on Windows, putty might work. I have not tried it.. but I guess it would work, since I see "putty" mentioned in the configuration page of #2. Thanks..

@Nagarjuna-Reddy you could perhaps use reload_config instead of rebooting but I haven't tried that.

@György-Farkas This problem was never figured out. Had to re-flash both devices to again make them accessible. However, you made a point about timing. I wasn't as patient as you. As such the first access to each device "post" upgrade wasn't actually post upgrade. This put both devices in some sort of munged up state. I'll attempt to force upgrade again, but this time chill out until the upgrade is over. thanks!! --Bill

@Hussein-Taher I also ran into this problem with a remote connection to my Omega. You should write not "local", but the IP address of your Omega in the network. For example, SSH root@omega-ABCD.192.168.3.1

@Diego-Pivaral said in What commands or keys should I press after copy-paste the ssh keygen into vi /etc/dropbear/authorized_keys: then I am lost when I need to update/close or register the public key, I do not know which commands I must type in the keyboard. Somebody is telling me is Control + O and Esc, but no result. I am using this tutorial: Assuming that the paste is successful, press the ESC key to enter vi mode, followed by :wq Where: ':' - enter command mode 'w' - write content out (save file) 'q' - quit (return to shell prompt)

@Ketsayay-Choohirun Effective troubleshooting. This is a good advice from @Chris-Stratton to you too. (Silicon Labs CP2102).

@Luciano-S. said in [Can't connect neither by serial nor ssh (exp dock)] @Chris-Stratton , did you see all the picture he posted? That was exactly my point. None of them show an attempt at using a serial connection. In terms of being in the wrong subnet, the ssh warning would not have resulted without connecting to something at a 192.168.3.1 running an SSH service, and while that could be a router, the comparably custom address makes it more likely that it actually was the Omega2.

SOLVED: It appears that the wifi chip you use does not support TKIP encryption. I switched the router to use AES and everything started working. You might want to document that. Mike